A mini tutorial on how AIMS/EIMS and MailBurst interact:
Handling incoming mail to david@domain1.com and david@domain2.com...
Here's what AIMS does when it gets mail for david@domain1.com
1) Is the domain listed in the Preferences' Server box?
2) Is there a POP mailbox with the name DAVID?
3) Is the <any-name> account enabled?
4) Perform what ever action is indicated by the settings for the <any-name>account.
So, if <any-name> is set to "Save as files..." to ":MailBurst:Mail"then MailBurst gets the email. If a message doesn't get to step 4, we'll never see it.
To handle multiple david's, you'll have to RENAME the DAVID POP mailbox (if you have one) to david01 (or some other unique name), and change his POP login name to david01.
Then add a Multi statement for david@domain1.com to go to david01, and david@domain2.com to go to david02 (note that addresses can be forwarded to other mail servers... they don't have to be POP mailboxes on your server).
The "david01" account could just as well be "id012324"... remember that this is ONLY the POP login name, NOT the user's email address. They should set their outgoing or REPLY address as david@domain1.com in their SMTP mail program (Eudora or Emailer, etc.) which will make their mail appear to be orignating from david@domain1.com, not david01@domain1.com
This stuff is hard, 'cause there's not much documentation for AIMS, so it's hard to put things together.
p.s. if you REALLY don't want to change the names of your existing POP
accounts, you can set up a second AIMS machine and have that server
as the front end mail processor, and have the second one contain all your
existing AIMS POP accounts. Then just forward mail from the main server
over to the second server. We have one client with 1500 mailboxes, and they
weren't about to change EVERYONE's POP mailbox name, but they DID want to
offer everyone a full set of names, like info, support, and of course, david
:-)